provider Releases POST /api/0/organizations/{organization_id_or_slug}/releases/
@utdk/sentry /api/0/organizations/{organization_id_or_slug}/releases/
Create a New Release for an Organization
Create a new release for the given organization. Releases are used by Sentry to improve its error reporting abilities by correlating first seen events with the release that might have introduced the problem. Releases are also necessary for source maps and other debug features that require manual upload for functioning well.
organization_id_or_slug path required
The ID or slug of the organization.
string

Try it

Authentication
Configure credentials for API Reference
Gateway
The gateway proxies requests and injects credentials server-side. Configure credentials above, then enter your gateway URL.

Saved automatically to browser storage.

createANewReleaseForAnOrganization
POST/api/0/organizations/{organization_id_or_slug}/releases/
Create a new release for the given organization. Releases are used by Sentry to improve its error reporting abilities by correlating first seen events with the release that might have introduced the problem. Releases are also necessary for source maps and other debug features that require manual upload for functioning well.

Parameters

required

The ID or slug of the organization.

Input

required

A version identifier for this release. Can be a version number, a commit hash, etc.

required

A list of project slugs that are involved in this release.

An optional commit reference. This is useful if a tagged version has been provided.

A URL that points to the release. This can be the path to an online interface to the source code for instance

An optional date that indicates when the release went live. If not provided the current time is assumed.

An optional list of commit data to be associated with the release. Commits must include parameters `id` (the SHA of the commit), and can optionally include `repository`, `message`, `patch_set`, `author_name`, `author_email`, and `timestamp`.

An optional way to indicate the start and end commits for each repository included in a release. Head commits must include parameters `repository` and `commit` (the HEAD sha). They can optionally include `previousCommit` (the sha of the HEAD of the previous release), which should be specified if this is the first time you've sent commit data. `commit` may contain a range in the form of `previousCommit..commit`.

Enter a gateway URL above to enable sending.

Code snippet
Updates live as you fill in the form above.

TypeScript

import sentry from '@utdk/sentry';

await sentry.createANewReleaseForAnOrganization()